home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Monster Media 1996 #15
/
Monster Media Number 15 (Monster Media)(July 1996).ISO
/
tribbs
/
mc10_02.zip
/
COMMENT.DOC
< prev
next >
Wrap
Text File
|
1996-04-26
|
8KB
|
170 lines
Customary Disclaimer:
Users of MULTI-COMMENT must accept this disclaimer of warranty:
THIS SOFTWARE AND ACCOMPANYING MATERIALS ARE DISTRIBUTED "AS IS"
WITHOUT WARRANTY, EXPRESS, IMPLIED OR STATUTORY, INCLUDING BUT NOT
LIMITED TO ANY IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS
FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL ANYONE INVOLVED WITH
THE CREATION AND PRODUCTION OF THIS PRODUCT BE LIABLE FOR INDIRECT,
SPECIAL, OR CONSEQUENTIAL DAMAGES, ARISING OUT OF ANY USE THEREOF
OR BREACH OF ANY WARRANTY.
This program was written utilizing Mark Goodwins TBAPI. TriBBS is
copyrighted by Mark Goodwin.
Copyright notice
=================
MULTI-COMMENT is a copyrighted program being distributed under the shareware
concept. As such, you may operate MULTI-COMMENT for a period of 30 days
without registering the software. After the 30 day evaluation period, you
must register your copy of MULTI-COMMENT of you will be in violation of the
United States and International copyright laws.
What it does
=================
MULTI-COMMENT is a replacement for the TriBBS internal comment to sysop.
The sysop has the ability to configure up to 10 people the user can choose
to leave the comment to. (It would be easy to add more, but does
anyone need more than ten?) An optional description for each sysop
can be included, and the sysop can configure which conference each sysop
is to receive their comment in. After the user chooses which sysop they
want to leave the message too, they enter the subject. If the conference
is an alias conference they will then be asked if they want to use their
alias. After that they go to the message editor. They can enter their
message, upload a message, or attach a file to their message. If they
choose to upload a message or attach a file TTPROT or FTTPROT is called to
process the upload. If the user attached a file it will be unarchived
if the proper archive for that file has been configured and exists in the
path. After the attached file is unarchived the virus scanner is called
to test the file if so configured. Scan, Thunder Byte, and F-Prot are
supported. When a user attempts to attach a file that already exists
in the MWORK directory they are informed that they can't upload that
file since it already exists. Also the minimum attachment security level
is comapred to the users security level, and if they don't have a high
enough level they will not have access to that option.
When the user saves the message it is recorded in the callers.log in the
same format as TriBBS uses.
Installing
=================
To install MULTI-COMMENT make a directory on you hard drive named MC
(or any other name you desire) and copy all of the program files into
that directory.
Next edit COMMENT.CFG to reflect your configuration. The included config
is already documented for all options so I will not document them again
here. MULTI-COMMENT uses DOOR.SYS as the drop file. When used off of a menu
TriBBS will generate the drop files, and MULTI-COMMENT will locate and use
the correct drop file. Edit your batch file to be executed when
TriBBS calls it and it will be ready to go.
The batch file for a single node bbs will look similar to the following:
CD\
CD\TRIBBS\MC\
COMMENT
CD\
CD\TRIBBS
BOARD
To replace the TriBBS internal Comment to Multi-Comment edit your
main.mnu in each nodes nwork directory as follows.
Was:
C,C,Comment To Sysop,0
Change To:
Z,C,Comment To Sysop,0
The batch file called when the user chooses comment will be MAINZ.BAT
in the above example.
**IMPORTANT** TTPROT or FTTPROT must be activated in the config. If
neither of them is activated the upload a message and
attach a file options will not be available!
**IMPORTANT** The directory for any unarchiver you use (PKUNZIP etc..)
and any scanner you use (SCAN etc..) and either TTPROT or
FTTPROT must be included in your path statment. When
Multi-Comment shells out to receive, unarchive, or scan a
file the path is searched for the specified EXE.
Multi-Node configuration
==========================
Multi-Node installation is fairly easy. Copy the files into their own
directory as above. Next make a cfg file for each node that will be
using multi-comment. You can name these files any legal dos filename,
but I would recomend naming them in such a way as to be helpful in
pointing out which node they belong to. For example NODE1.CFG, NODE2.CFG,
etc. Edit the cfg for each node so that the BBSDIR parameter points
to that node's directory, and edit the Node parameter to reflect the proper
node number. (Share.exe should be loaded in your autoexec.bat also.) Next
make the batch file for each node. They will be the same as the above
except be followed by the name of the cfg file. MULTI-COMMENT loads
COMMENT.CFG by default. The command COMMENT NODE1.CFG will override the
default and load the NODE1.CFG. That's all there is to multi-node use,
just make sure that you have a seperate cfg for each node, and that it
points to the proper node dir.
Menu's
==================
Included with Multi-Comment are two sample menu's SYSMENU.ANS and ASC.
If these menus exist when Multi-Comment is executed they will be displayed
instead of the internal menu. You can optionally use a SYSMENU.RIP menu if
you wish to make one. The only thing you need to make sure when making
your menu is that you try and keep it about 1/2 screen in size so that it
doesn't scroll as additional input is requested from the user. Each sysop
listed in your menu must be included in the COMMENT.CFG, and must be in the
same order. (Sysop one in the custom screen must be the same as sysop one
in the config.)
The Rip detection routine used in the door driver I use does not always
detect Rip properly with some terminals. I have been assured that this
has been fixed in the updated driver which should be released soon. Because
of this SYSMENU.RIP may not be displayed for all RIP callers. If the
rip detection fails SYSMENU.ANS will be displayed instead. Also RIP is
never displayed in the local screen. The new driver is rumored to support
local rip so that may be a feature in the future.
TEMPn
==================
Multi-Comment will create a temporary directory in it's working directory
for each node that uses it. This directory will have the name Temp1 for
node 1, Temp2, for node 2 etc. When Multi-Comment is called this directory
is created if it doesn't already exist. This temporary directory is used
to temporarily store an uploaded message, or attached file while they are
being processed. Upon exit and startup the contents of this temporary
directory are cleaned out.
Shareware limitations
======================
The only limitation to Multi-Comment is an unregisterd message when the door
is first executed. The registered version will not display this message.
Registration
======================
If you like Multi-Comment and would like to register it fill out the
registration form included in this archive. Registration is only $5.00.
Suggestions
=====================
If you would like something added to Multi-Comment drop me a note, if I
like the idea I will add it if possible.
If you have an idea for a TriBBS 10.0 utility that you can't find drop
me a line and explain it. I may already be working on it, but if I'm
not and do make the utility I will give you a free registration for the
suggestion. My contact information is included in the registration form.
Acknowledgments
=====================
Torrance Jones. Suggested that the conference the comment is posted in
be made configurable.